Open topic with navigation

System Requirements and Capacities

Paradigm LightDesigner can be installed by running the setup installer on a PC running Windows 7 or Windows 10.

Minimum Computer Requirements

• Windows 7 or Windows 10
• 2.7 GHz Intel processor
• 32 MB or better non-integrated graphics chip with OpenGL 2.0 support
• 4 GB RAM
• 2 GB available SSD or HD storage
• Display capable of 1920 x 1080 resolution or greater
• 10/100/1000 BaseTX Ethernet
• USB Port
• Keyboard
• Mouse / Trackpad / Trackball

Unison Paradigm System Capacities

It is highly recommended that you refer to the System Estimator View to provide visual indication of your system in its current state compared to the maximum.

In addition to the capacities defined in the Server Project and Project sections below, a Paradigm system is limited to the following Echo Expansion Bridge and Paradigm Mobile Application capacities:

• Up to 16 Echo Expansion Bridges (EEB) may be assigned to an individual P-ACP
• Each Echo zone counts against the P-ACP's 1,024 maximum channel count; therefore reducing the number of spaces and zones an EEB uses will reduce the overall impact on the P-ACP channel count.

  Note: Use care when configuring your system with Echo Expansion Bridges. A connected Echo system that includes 16 spaces, 16 zones, and 4 Echo Expansion Bridges would utilize 1,024 channels. This would consume the entire capacity of a P-ACP leaving no room to patch additional DMX/sACN addresses.

• Up to 128 EEBs are allowed per individual Project or Server Project.

  Note: Adding a server to a project will not increase the maximum allowed EEBs per Paradigm system.

• Up to 16 Paradigm Mobile Button Station instances per P-ACP.

Server Project Capacities

• A Server Project must be accompanied by a Paradigm Central Control Server (P-CCS)
• A Server Project must include at least one project (sub-project) with at least one Paradigm Architectural Control Processor (P-ACP).
• A Server Project can support a maximum of 64 projects and a total maximum of 64 Paradigm Architectural Control Processors (P-ACPs).
• A Server Project can support a maximum of 32 Virtual Touchscreen Stations (VTSs).

Project Capacities

• Up to 12 Paradigm Architectural Control Processors (ACP) in a project.
• Up to 1,024 Channel outputs per Paradigm ACP.
• Up to 128 control stations (including LinkConnect, Ethernet, and Mobile Button) per Paradigm ACP.
• Up to 5 Network Station Power Supplies (P-NSPS-D) per Paradigm ACP.
• Up to 16 Paradigm Mobile Button Station instances per Paradigm ACP.
• Up to 63 control stations per Paradigm Station Power Module (P-SPM-E).
• Up to 63 control stations per Network Station Power Supply (P-NSPS-D).
• Up to 18 Paradigm Touchscreen Stations, including wireless Handheld Touchscreens, per Paradigm ACP (up to 6 can be LinkConnect with the appropriate auxiliary power supply).
• Up to 4 LinkConnect Paradigm Touchscreen Stations per Station Power Module or Station Repeater Module..
• Up to 4 LinkConnect Paradigm Touchscreen Stations per Network Station Power Supply with an added 30 W auxiliary 24 VDC supply.
• Up to 32 Wireless Access Stations (P-LCD-WAS) are allowed per Paradigm Architectural Control Processor. A maximum of 16 are allowed per Station Power Module or Station Repeater Module.
• Up to 18 Handheld Dock Stations (P-LCD-DOCK) are allowed per Paradigm Architectural Control Processor.
• Up to 65535 Timed Event Exceptions.
  • Up to 365 old (expired) instances per Timed Event Exception.

Echo Expansion Bridge and Echo System Capacities

• Each Echo Expansion Bridge (EEB) has 4 Echo segments (each powered by an external Echo power supply) and each supporting 16 output products and 16 control products.
• A total maximum of 64 output products and 64 control products are allowed per Echo system
• All devices connected to an Echo Expansion Bridge will share the same 16 Echo spaces.
• The EEB can be powered using 24 VDC or Power over Ethernet (PoE).
• EEBs do not communicate with each other.
  • Echo controls connected to the EEB cannot control anything outside of its own connected Echo system.
  • You may not connect an Echo segment of one EEB to the segment of another EEB, nor can you connect segments of a single EEB to another.

EEBs used in a Paradigm System:

• The EEB allows control of connected Echo systems from within the Paradigm system where features to monitor and control Echo presets, Echo zones, space combine, and space lockout from any Paradigm control, including timed events are possible.
• An EEB's configuration can be edited both using the EchoAccess Mobile App or LightDesigner Software, and is saved as part of the Paradigm project configuration file.
  • LightDesigner Software can upload and retrieve the EEB configuration data separate from the main Paradigm configuration file, but Live Edit of the EEB configuration data is not possible from LightDesigner Software.
• When used in a LightDesigner Software configuration, the EEB is associated with an individual Paradigm ACP.
• EEBs can be added to a Paradigm configuration in LightDesigner Software by dragging the object from the "ETC Paradigm" station library into the any space.
  • An EEB cannot be added to the space of any other EEB.
  • EEB spaces can be edited in the LightDesigner Software Plan view using the Design view.
• EEBs cannot allow Echo control products to trigger or control Paradigm.